Realtime, verified and automated demand response energy saving controller

ABSTRACT

Energy saving devices and methods for HVAC or other energy consuming systems and particularly plug and play energy saving controllers adapted to predict energy usage and savings, such as by extending the fan run time of HVAC systems after the heating or cooling unit has shut off and/or by stopping the compressor or heater for a short duration of time if the compressor or heater has been running continuously for fixed periods of time, while the fan is still blowing, wherein the energy saving controller is integrated with a wireless-enabled, real-time measurement and verification system, and with demand response capability.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part and claims the benefit of U.S. Non-Provisional application Ser. No. 16/036,796 filed Jul. 16, 2018, which is a continuation-in-part and claims the benefit of U.S. Non-Provisional application Ser. No. 15/787,672 filed Oct. 18, 2017 (now U.S. Pat. No. 10,174,966), which is a continuation-in-part and claims the benefit of U.S. Non-Provisional application Ser. No. 15/093,669 filed Apr. 7, 2016 (now U.S. Pat. No. 10,119,719) and of U.S. Non-Provisional application Ser. No. 15/344,483 filed Nov. 4, 2016 (now U.S. Pat. No. 10,066,849), said application Ser. No. 15/093,669 filed Apr. 7, 2016 being a continuation-in-part of U.S. Non-Provisional application Ser. No. 14/628,159, filed Feb. 20, 2015, (now U.S. Pat. No. 10,047,969) which in turn is a continuation-in-part of U.S. Non-Provisional application Ser. No. 14/332,714, filed Jul. 16, 2014 (now abandoned) and U.S. Non-Provisional application Ser. No. 14/016,012, filed Aug. 30, 2013 (now U.S. Pat. No. 9,410,713), and all prior applications are hereby incorporated by reference, to the extent that they are not conflicting with the present application.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The invention relates generally to energy saving devices and methods for HVAC or other energy consuming systems and particularly to a plug and play energy saving controller (ESC or EFC) to predict energy usage and savings such as by extending the fan run time of HVAC systems after the heating or cooling unit has shut off and/or by stopping the compressor or heater for a short duration of time if the compressor or heater has been running continuously for fixed periods of time, while the fan is still blowing, wherein the controller is integrated with a WIFI enabled real time measurement and verification system and with demand response capability (“MVDR”).

2. Description of the Related Art

There are several energy saving devices, equipment, energy saving measures, techniques and methodology, hereinafter referred to as a “Third-Party Devices,” on the market today. The purpose of such third-party devices is to increase the efficiency and to reduce energy consumption of the original energy consuming equipment and system, such as HVAC systems, within a facility. These Third Party Devices may include programmable thermostats, WiFi-enabled thermostats, motion detector thermostats and lightning systems, room occupancy detector controller, energy saving controllers, fan extension switches, efficient fan controllers, automatic ON/OFF switches, energy savings actuators, energy saving relays, energy saving light dimmers, variable speed motors, ECM motors, etc., and energy saving measures including cleaning of air ducts and air filters, fault detections, proper charging of the refrigerant lines, insulating the refrigerant lines, sealing of air ducts, maintaining a certain air ducts pressures, and so on.

Most third-party devices rely on historical data, formulae, mathematical models, engineering calculations, field studies, white papers, laboratory testing, controlled testing, and a set of assumptions in order to come up with a method of calculating deemed savings. Many systems utilize data logging equipment, which record data over a fixed period of time (for example, over 30 days period) in order to acquire a bench mark and develop sophisticated algorithms. These algorithms project the deemed savings achieved after installing the third-party device. However, there are no actual real-time, continuous verifications of the actual performance of such Third Party Devices and real-time responsive control of the energy consuming equipment via the Internet.

Third Party Devices connected to an energy consuming equipment such as HVAC systems, pool pumps, refrigeration units, lighting systems are not typically monitored on a permanent basis. They are not data logged continuously in real time to measure and verify the deemed or claimed energy savings. Moreover, many of the Third Party Devices are not even WiFi enabled and/or remotely controlled via the Internet.

HVAC (Heating Ventilating and Air Conditioning) systems include temperature changing components for changing the temperature and condition of air. Indoor air handlers drive air from the temperature changing component through supply ducts to zones within a building. A typical HVAC consists of heating unit, air conditioning or cooling unit or heat pump unit, and the fan or blower at the air handler unit. A thermostat is used to control the conditions of the air in a conditioned space by sending control signals to the HVAC's relays or contactors to activate or deactivate one or more of the temperature changing components.

An HVAC System typically runs a ventilation blower fan for an additional 0 second to 90 seconds after the heating or cooling unit has been turned off. As an example, the heating unit could be a furnace and the cooling unit may be an air conditioner cooling compressor coil. Studies have shown that even after this duration, the furnace surface or the air conditioner cooling coil still have some energy available to heat or cool indoor air. For example, most furnace heat exchangers are still hot (above 135 to 210° F.) after the furnace fan turns off. This wasted energy is not delivered to the conditioned space when the fan stops blowing. However, unless an MVDR is installed to measure and verify this, this energy cannot be quantified or proven by actual performance data.

Studies have also shown that if the cooling unit has been running continuously for a period of time of 20 minutes to 30 minutes, the cooling coil is wet and the evaporating water from the wet coil can provide additional cooling energy, which HVAC systems often fail to harness. Additionally, if a heating unit has run continuously for a period of time of 20 to 30 minutes, the furnace often reaches its maximum temperature. An HVAC system often continues to run a heating unit after the furnace reaches its maximum temperature, which wastes residual heat energy and reduces the life of a furnace. Unless an MVDR is installed, the true amount of heating and cooling energy lost is often unknown and unquantified.

There are several WiFi or other wireless enabled devices in the market place. For thermostats, the majority of those available in the market are WiFi enabled type where the user can remotely adjust the set temperature, turn the A/C unit on or off, etc. There are also many manufacturers of WiFi enabled switches to turn a device or a piece of equipment on and off. There are also many Internet of Things (TOT) devices that monitor and control connected equipment remotely. However, no such devices are used to record measurements and verifications of the actual energy saved so as to provide additional controls for energy consuming equipment or devices.

Thermostats that are controllable via Wi-Fi are gaining in popularity as they allow users the flexibility of remote controls. A user can remotely turn the thermostat on or off, set the scheduling and increase or decrease the temperature set points from anywhere in the world where there is Internet or mobile data connectivity. With the advent of the Wi-Fi enabled thermostat, and its widespread use, the utility providers such as Southern California Edison, for example, are implementing demand response (DR) using these thermostats.

DR is a set of actions taken to reduce electrical loads when the utility's electric grid could be overloaded due to excessive demands by the consumer. This is done by increasing the varying electricity rates where the demand for electricity is higher than the supply. Traditionally, an electricity rate was highest around 11 am to 2 pm when power consumption is at its peak and lowest around midnight when power consumption is at its lowest. With the widespread installation of solar panels, however, the peak hours in many places have shifted to 4 pm to 5 pm when the sun starts to set. Even with electricity rates at its highest during the peak periods, there are times when the peak usage is still more than what the utility can supply that may cause brownouts or rolling blackout.

A quick solution would be to increase the capacity of the generating power plants, but that would mean high investments, more pollution, more greenhouse effects, etc. A better solution could be to conserve energy during peak usage periods. As a way to conserve energy, many utility providers have begun issuing rebates and other incentives to consumers, in return for said consumers allowing the utility provider access to their high power consuming devices, such that the utility provider can turn off said power consuming devices for a number of times per year.

A method utility providers can use to turn off power consuming devices is Automatic Demand Response (ADR), which allows for fully automated signaling from the utility provider to provide automated connectivity to the consumer's power consuming equipment to have access and control this equipment.

Open ADR is a research and standards development effort for energy managements. Open ADR provides a foundation for inter-operability of information exchange to facilitate the automated demand response. Its application is to send information and signals to cause electrical power consuming devices to be turned off during periods of high demands.

Open ADR Alliance is composed of industry stakeholders that are interested in fostering the deployment of low cost and reliable demand response communication protocols and the adoption of the common Open ADR standards. In this way, various devices produced by the manufacturers in the alliance can work with each other and with the Open ADR standards and protocols.

A WI-FI enabled thermostat with Open ADR certification is currently used by the Utility provider to manage the electrical power consumed by heating ventilation and air conditioning system (HVAC). HVAC systems are one of the largest consumers of electrical energy. So, if a Utility provider has the ability to control hundreds of thousands of HVAC by temporarily turning the compressor off when brownout is expected in a specific grid, then blackouts can be avoided. Also, the Utility would not need to add more power plants just to service the peak demands periods.

An example of the rebate program offered by the Utility provider to its consumers is to provide free Wi-Fi enabled thermostat at no cost to the facility owner provided the facility owner allows the Utility provider to shut off the HVAC system for 10 times per year for 30 minutes per occurrence. In other instances, the rebate provided could be offering credits against the utility bill. Since these thermostats have Open ADR certification, the Utility provider is able to access these registered thermostats automatically and using automated software to carry out the program.

However, there are many homeowners who may be interested in the rebate programs, but do not wish to have their existing thermostat replaced with the WI-FI enabled thermostat. Most WI-FI enabled thermostats are complicated to set up as it involved setting up the Wi-Fi and typically is not a plug and play device. Hence, learning curve to learn and use the WI-FI enabled thermostat may be too cumbersome and technical for many home owners.

Therefore, there is a need for a new and improved controller to address the issues outlined above.

Particularly, to minimize the limitations found in the prior art, there is a need for a Wi-Fi or other wireless enabled MVDR device that can be connected between an existing energy savings Third Party Device and the energy consuming equipment such as an HVAC system, pool pumps systems, refrigeration system, lighting systems, etc., where the automated demand response can be implemented without having the need to replace any of the existing or originally installed devices. Further, there is a need for a wireless (e.g., Wi-Fi) enabled MVDR circuit device with open automated demand response capability that allows energy efficient operation of the energy consuming equipment during regular operations outside of a demand response occurrence, to save even more energy.

The problems and the associated solutions presented in this section could be or could have been pursued, but they are not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches presented in this section qualify as prior art merely by virtue of their presence in this section of the application.

BRIEF SUMMARY OF THE INVENTION

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key aspects or essential aspects of the claimed subject matter. Moreover, this Summary is not intended for use as an aid in determining the scope of the claimed subject matter.

In an embodiment a new plug and play energy saving controller (ESC) is provided to predict and extend the fan run time of HVAC systems after the heating or cooling unit has shut off and/or to stop the compressor or heater for a short duration of time if the compressor or heater has been running continuously for a fixed period of time, but with the fan still blowing. Thus, an advantage is the harnessing of otherwise wasted heating or cooling energy from the HVAC systems. Monitoring the previous cycle(s) for the compressor or heater on and off durations gives a better, more intelligent, comprehensive and efficient fan extension period, to save more energy. Further, shutting down the compressor or heater if they run continuously for, for example, 30 minutes, but keeping the fan running, will act like a fan extension and it saves energy.

In another embodiment, the new plug and play controller is inserted between the thermostat and the air handler unit. Thus, another advantage is the ease of installation of the controller.

In another embodiment, the controller can be made as part of the thermostat itself saving a separate device to be connected between the thermostat and the air handler unit.

In another embodiment, the controller can be made as part of the air handler unit control board itself saving a separate device to be connected between the thermostat and the air handler unit.

In another embodiment the new plug and play controller is configured to change the unknown state of the thermostat's fan, cool or heat controller circuitry into a known state when the thermostat is switched to off or when the thermostat malfunctions. Thus, another advantage is the increased versatility of the provided controller by making it capable of functioning properly in connection with various manufacturers' thermostats.

In another embodiment, a new plug and play energy saving controller (ESC/EFC) provides a Wi-Fi enabled circuit device for open automated demand response capability, thus eliminating the cumbersome, challenging and/or expensive task of replacing the entire thermostat, while still accomplishing the goal of the DR/ADR to save energy.

In another embodiment, in addition to providing a Wi-Fi enabled circuit device for open automated demand response capability, the new plug and play energy saving controller provides a circuitry for ensuring energy efficient operation of the HVAC system outside of a demand response occurrence, thus further saving energy.

In another embodiment, a new WiFi Enabled Controller (MVDR) is provided to measure and verify the performance of any Third Party Device (as defined above) connected to one or more original or existing energy consuming equipment in a facility. Thus, an advantage is to verify the actual energy saved in real time instead of using deemed or calculated energy saved from installing the Third Party Device and the ability to further control either of these Third Party Devices or the originally installed energy consuming equipment. Then, the actual energy saved can be submitted to the utility providers such as PG&E, SCE, SDG&E or program managers to claim the rebates as part of the public benefits programs for energy efficiencies measures.

In another embodiment, as an example, a WIFI or wireless enabled MVDR is provided to do all of the following: (1) provide measurement and verification of real energy saved of any connected Third Party Device to one or more original energy consuming equipment with the capability to further control these energy consuming equipment; (2) interface with the various original energy consuming equipment such as HVAC unit, pool pumps, refrigeration units, lighting system, etc., to provide real time measurement and verification of real savings from the installation of a piece of an energy saving equipment (Third Party Device); (3) permanently and continuously data log and stream the data in real time to a remote server such as Amazon Cloud Server, etc; (4) analyze the real time streamed data, compute and implement in real time further improvement in the efficiency of these original equipment and also to remotely control the Third Party Device to further improve on its effectiveness; in an example, the control may include remotely shutting down lights in the house controlled by a third party light controller connected to and controlled by the MVDR; (5) remotely adjust original equipment's operational parameters or the Third Party Device's operating parameters to recover additional energy loss and to operate the original equipment at higher efficiency; in an example, adjusting parameters may include remotely deeming lights controlled by a third party light controller connected to and controlled by the MVDR.

In another embodiment, the new MVDR can also have a built-in energy saving features and can therefore itself also function as a Third Party Device plus the measurement and verification device all in one combination unit. Thus, another advantage is the dual use purpose.

In another embodiment, the new MVDR can be made as part of the thermostat itself eliminating a separate device to be connected between the thermostat and the air handler unit.

In another embodiment, the new MVDR can be made as part of an HVAC's air handler unit control board eliminating a separate device to be connected between the thermostat and the air handler unit.

In another embodiment, the new MVDR can be made as part of a pool pump controller unit eliminating a separate device to be connected to the pool pump controller.

In another embodiment, the new MVDR can be made as part of a refrigeration controller unit of a refrigerator, freezer, cooler or chiller eliminating the need to install a separate device to be connected to the refrigeration unit.

In another embodiment, the new MVDR can be made as part of a lighting control system in a facility eliminating a separate device to be connected to the lighting systems.

The above embodiments and advantages, as well as other embodiments and advantages, will become apparent from the ensuing description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

For exemplification purposes, and not for limitation purposes, embodiments of the invention are illustrated in the figures of the accompanying drawings, in which:

FIG. 1 illustrates a schematic circuit diagram of an integrated circuit for controlling the fan, the compressor and the heater of a heating, ventilation and air conditioning (HVAC) system.

FIG. 2 illustrates a block diagram for controlling the fan, the heater and the AC of an HVAC system using the integrated circuit from FIG. 1.

FIG. 2a illustrates a modified block diagram of FIG. 2.

FIG. 3 is a block diagram illustrating that the integrated circuit from FIG. 1 can be part of the air handler control board.

FIG. 4 is a block diagram illustrating that the integrated circuit from FIG. 1 can be part of the thermostat.

FIG. 5 is a block diagram of an exemplary process flow of a wireless energy saving controller, according to another embodiment.

FIG. 6a-b are block diagrams of an HVAC system incorporating a wireless energy saving controller (“WiFi ESC”), as disclosed hereinafter, according to another embodiment.

FIG. 7 is a flow chart illustrating the hardware and firmware architecture of a WiFi or wireless enabled MVDR, according to an aspect.

FIG. 8 illustrates the functional block diagram of the hardware of the MVDR, according to an aspect.

FIG. 9 illustrates a flow chart detailing an exemplary method for a user to interface between the MVDR hardware and the remote server, according to an aspect.

FIGS. 10a-b illustrate exemplary installs of a plurality of MVDRs on an HVAC air handler unit 1000 and an HVAC compressor 1008, according to an aspect.

FIGS. 11a-c illustrate additional exemplary MVDR installs, wherein the MVDR is integrated into a refrigeration unit, lighting appliance, and pool pump, according to an aspect.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

What follows is a detailed description of the preferred embodiments of the invention in which the invention may be practiced. Reference will be made to the attached drawings, and the information included in the drawings is part of this detailed description. The specific preferred embodiments of the invention, which will be described herein, are presented for exemplification purposes, and not for limitation purposes. It should be understood that structural and/or logical modifications could be made by someone of ordinary skills in the art without departing from the scope of the invention. Therefore, the scope of the invention is defined by the accompanying claims and their equivalents.

FIG. 1 illustrates a schematic circuit diagram of an integrated ESC circuit 100 for controlling the fan, the compressor and the heater of a heating, ventilation and air conditioning (HVAC) system. Preferably, the integrated circuit 100 comprises an input port 101 having a plurality of input terminals 101 and a plurality of output terminals 102, a voltage regulator 107, a microprocessor 103, transistors 109, 110, 111, 104, 105 and 106, and triacs 112, 113 and 114, whereby at least one of the plurality of input terminals 101 switches the transistors 109, 110 or 111 to a conducting state that turns on the microprocessor 103 which creates a trigger signal to turn on at least one of the plurality of triacs 104, 105, 106 which provides an output 102 of circuit 100 that enables the switching OFF or ON of at least one of the output terminals to ground.

The plurality of input terminals 101 connects the integrated circuit 100 to the thermostat of a HVAC system. The plurality of input terminals 101 includes typically a first input terminal 115, a second input terminal 116, a third input terminal 117, a fourth input terminal 118, and a fifth input terminal 119. The input terminal 119 has typically a common terminal voltage of 24 Vac with reference to the ground node of circuit 100.

The input terminal 118 gets its input from the thermostat's red color coded wire. In circuit 100, the terminal 118 is at 0 vac with reference to the ground node.

The input terminal 115 gets its input from the thermostat's fan output line which is typically either a 24 vac or a 0 vac level. Sometimes, this line may be at floating state as described earlier. The input terminal 116 gets its input from the thermostat's heat output line which is either a 24 vac or a 0 vac levels. Sometimes this line may be in high impedance state. The input terminal 117 gets its input from the thermostat's cool output line which is either a 24 vac or a 0 vac levels. Sometimes this line may also be in high impedance state.

The voltage regulator 107 acts as a constant voltage source to provide a constant voltage to the microprocessor 103 and the transistors 109, 110,111, 104, 105 and 106.

The voltage regulator 107 is preferably fed from the output of a series of diodes 120 or diodes and current limiter 108. The capacitor 122 and Zener diode 121 are connected in parallel to the voltage regulator 107. The capacitor 122 and the Zener diode 121 provide a constant voltage to the voltage regulator 107. The capacitor 122 and the Zener diode 121 are connected in parallel with a variable voltage source and acts as voltage regulators to regulate the voltage across the voltage regulator 107. The Zener diode 121 clamps the voltage to the maximum specified voltage across the input terminal of the voltage regulator 107. The integrated circuit 100 has a parallel pair of output capacitors 123 to maintain the voltage regulator 107 output supply voltage.

The microprocessor 103 has a plurality of terminals 124 to provide triggering signals to the base of transistors 104, 105 and 106. Transistors 104, 105 and 106 are acting as drivers to provide drive signals to turn on or off the triacs 112, 113 and 114. The output terminals 102 are the outputs of triacs 112, 113 and 114.

As an alternate embodiment, the triacs 112, 113 and 114 can be replaced with any switchers, such as relays, contactors or multiplexers.

The plurality of output terminals 102 connects the integrated circuit 100 to the air handler unit of a HVAC system. The plurality of output terminals 102 includes a first output terminal 124, a second output terminal 125, a third output terminal 126, a fourth output terminal 127, and a fifth output terminal 128. The output terminal 128 has a common terminal voltage of 24 vac with reference to circuit 100's ground node. The output terminal of 127 is the red color coded wire which is at 0 Vac with reference to circuit 100's ground.

The output terminal 124 goes to the air handler unit's fan input. Output terminal 125 to the air handler unit's heat input. Output terminal 126 to the air handler unit's cool input.

The turn on or turn off actions of the triacs 112, 113 and 114 will enable output terminals 124, 125 and 126 to be connected to ground or be in high impedance state. These in turn will control the operations of the air handler unit's solenoids to activate or deactivate the contactors or relays of the blower fan, compressor and gas/electric heater.

The plurality of terminals 124 of the microprocessor 103 includes a supply voltage terminal 129, a ground terminal 130, drive output terminals 131, 132, 133, and input terminals 134, 135, 136.

Terminal 134 of microprocessor 103 is driven by the collector of transistor 111 and the output of a control circuit derived from the input 117. This control circuit includes resistor 137, the output of voltage regulator 107, resistor 138, reverse biased diode 139, resistor 142, input 117, a pair of parallel resistors 143 and the input (common) terminal 101.

Similarly, terminal 135 of microprocessor 103 is driven by the collector of transistor 110 and a control circuits derived from the input 116.

Similarly, terminal 136 of microprocessor 103 is driven by the collector of transistor 109 and a control circuits derived from the input 115.

Transistors 109, 110 and 111 are npn transistors that act as switching elements and together with outputs derived from the inputs 116, 117 and 118 are connected to the microprocessor 103 to manipulate the output signals.

The base of transistor 111 is connected to input (cooling) terminal 117 and input (common) terminal 119, by a pair of parallel resistors 143 in series with resistor 142 and in series with diode 139, in series with resistor 140 and diode 141. The base of the transistor 111 has a capacitor 144 and a resistor 145 connected across and to ground. The collector of the transistor 111 provides the input to terminal 134 of the microprocessor 103 which controls the output (cooling) terminal 126. The emitter of transistor 111 is connected to circuit 100 ground.

Similarly, the same logic circuits applies for input (heater) terminal 116 to control the output (heater) terminal 125, and for input (fan) terminal 115 to control the output (fan) terminal 124.

The integrated circuit 100 has the diodes 120 in forward bias and diodes 139, 146 and 147 in reverse biased. The circuit 100 enables switching the HVAC fan to OFF if the thermostat fan output is in OFF or float or unknown state. Similarly, the circuit 100 enables switching the HVAC heater to OFF if the thermostat heat output is in OFF or float or unknown state. Similarly, the circuit 100 enables switching the HVAC cooling compressor to OFF if the thermostat cool output is in OFF or float or unknown state.

The circuit 100 process the float state of the thermostat output signals as it enters into circuit device 100 through input terminals 115, 116 and 117 and then outputs an OFF state signal in output terminals 124, 125 and 126.

The microprocessor 103 is programmed for energy efficient operation of the HVAC system by extending the fan run time of the HVAC blower fan based on the energy left over in the heater elements or in the air conditioning cooling coil and/or the rate of energy transfer (i.e., how fast the room gets heated up again in the case of a cooling cycle, or how fast the room gets cooled down again in the case of a heating cycle), as it will be described in more details hereinafter. The rate of energy transfer may be obtained by monitoring the on-off periods of prior cycles to estimate temperature differences between inside and outside and thus the rate at which the room is heated up or cooled down by its environment during the OFF period after the thermostat sends a command signal to have the HVAC fan shut off. Additionally, if the compressor (or heater, if HVAC system is in heating mode) has been running continuously for a predetermined period, for example, approximately 20-30 minutes, the microprocessor 103 will shut down the HVAC compressor (or heater) for, for example, 3 to 5 minutes while the fan continues to run, even though the thermostat did not send a command signal to have the compressor (or heater) shut down. The above two actions (i.e., extending fun run time and shutting the compressor or heater briefly) are independent of each other and controlled by the microprocessor 103. Shutting down the compressor or heater if they run continuously for, for example, 30 minutes, but keeping the fan running, will act like a fan extension and it saves energy.

The input terminal 115 voltage changes depending on the ON/OFF position of the fan. The first input terminal 115 is coming from the thermostat fan output command signal (color coded green wire) and has a voltage selected from a group consisting of 24 vac, 0 vac and a floating value. The floating value means that the input terminal 115 is not connected to either 24 vac or 0 vac, and can assume any value. The input terminal 119 always has a common terminal voltage of 24 vac with reference to circuit's 100 ground.

In a typical operation of a thermostat, a 24 vac thermostat output is an OFF state and ground or 0V thermostat output is an ON state. So, the thermostat turns on the fan by outputting a 0 vac to the fan wire, etc. When the thermostat wants to turn OFF the fan, the input (fan) terminal 115 of circuit 100, and the input (common) terminal 119 of circuit 100 both has 24 vac. The reversed biased diode 147 allows negative portion of the 24 vac from input terminal 115, after passing through resistor 155, to be present at the anode of diode 147. The RMS voltage at the anode of diode 147 derived from input terminal 115 in series with resistor 155, is at least a negative 10 Vrms. From input (common) terminal 119, approximately 5 VDC from the voltage regulator 107 in series with resistor 148, is also present at the anode of the diode 147. The resultant of the RMS voltage and the DC voltage is always negative which charges the capacitor 149 with a negative voltage as well. The diode 150 blocks this voltage from the base of transistor 109. The resistor 151 pulls the voltage of the base of transistor 109 to ground and cause the transistor 109 to be in off state. So, the input terminal 136 to microprocessor 103 is approximately 5 vdc high from the output of voltage regulator 107 in series with resistor 153. The microprocessor 103 will manipulate its output 131 to low (0 volt) causing transistor 106 to shut off. This in turn shuts off the triac 112 and causes the circuit 100's fan output terminal 124 to be in high impedance state which turns the HVAC fan to off.

When the input terminal 115 has 0 vac or ground, and the input (common) terminal 119 has 24 vac, the 24 vac of terminal 119 in series with resistor pairs 156 sinks to ground as the outputs of resistor pair 156 is connected to the input terminal 115 which has 0 vac.

The anode of reverse bias diode 147 is now high from the 5 vdc through resistor 148. The positive voltage at the anode of diode 147 cause the capacitor 149 to be charged to a positive voltage which in turn cause the forward bias diode 150 to conduct and turns on transistor 109. When transistor 109 conducts, the microprocessor 103's terminal 136 becomes low. Microprocessor 103 manipulates its output 131 to high and turns on transistor 106 which in turn turns on triac 112. The circuit 100's output (fan) terminal 124 becomes 0 vac which turns on the fan of the HVAC system.

When the circuit 100's input terminal 115 is in floating state, the input 115 is not connected to either 24 vac or 0 vac. In the floating state, the voltage at terminal 115 is unknown. The voltage at terminal 119 has 24 vac flowing through the pair of parallel resistor 156. The reverse bias diode 147 allows negative portion of this 24 vac to be present at the anode of diode 147 which will charge the capacitor 149 to a negative voltage. The diode 150 blocks the negative voltage to the base of transistor 109, and the resistor 151 pulls the base of transistor 109 to ground turning transistor 109 to off state. This in turn cause a 5 vdc present at terminal 136 of microprocessor 103 which cause 131 to go to low voltage shutting off transistor 106 and putting the triac 112 to off state. The circuit 100's output (fan) terminal 124 stays at high impedance state and the HVAC's fan is at OFF state thereby solving the problem of the floating inputs into terminal 115.

Similarly, the above applies to circuit 100's input (heater) terminal 116 and input (cooling) terminal 117 which can solve the floating states to these inputs.

FIG. 2 illustrates a block diagram of an integrated circuit 201 for controlling the fan 203, heater 204 and AC 205 of a HVAC Air Handler Unit 200. The integrated circuit's 201 configuration, and more specifically that of its controller 218, may be as that of the integrated circuit from FIG. 1. The HVAC 200 includes an air conditioner (AC) 205, a heater 204 and a fan 203 and the wire color coded green with its terminal 206, wire color coded white with its terminal 207, wire color coded yellow with its terminal 208, wire color coded red with its terminal 209, and a 24 VAc common wire and its terminal 210.

The integrated circuit 201 is as shown connected between the thermostat 202 and the HVAC air handler unit 200. The integrated circuit 201 includes output connectors 211, input connectors 212 and the controller 218. The output connectors 211 have wire lead terminals or screws terminals 214, 213, 215, 216 and 217 to connect to the HVAC 200. The input connectors 212 have wire lead terminals or screw terminals 222, 223, 221, 220 and 219 to connect to the thermostat.

From the output connector 211, the wire from the G terminal 214 is connected to the G terminal 206 of HVAC 200, wire from W terminal 213 is connected to the W terminal 207 of HVAC 200, wire from Y terminal 215 is connected to the Y terminal 208 of HVAC 200, wire from C terminal 216 is connected to the C terminal 210 of HVAC 200 and the wire from R terminal 217 is connected to the R terminal 209 of HVAC 200.

From the input connector 212, the wire from the G terminal 222 is connected to the G terminal 224 of thermostat 202, wire from W terminal 223 is connected to the W terminal 225 of thermostat 202, wire from Y terminal 221 is connected to the Y terminal 226 of thermostat 202, wire from C terminal 220 is connected to the C terminal 227 of thermostat 202 and the wire from R terminal 219 is connected to the R terminal 228 of thermostat 202.

When the thermostat 202 sends any control command instructions through its fan, heat or cool outputs, these instructions go into the integrated circuit 201, which acts as an energy saving controller (ESC) by manipulating these instructions and sending a revised set of energy savings command instructions to the HVAC 200, as disclosed herein. Further, the integrated circuit 201 continuously monitors the status of the thermostat 202, and will turn off the fan, heater or compressor if it detects a float or high impedance state of thermostat 202 due to a variety of reasons.

The ESC will adjust the fan operation automatically for heating using an algorithm derived from the stored energy left after furnace or heat pump has shut down and the rate at which the condition of the room is changed by its environment after the heater or air conditioning are in OFF condition. The algorithm will preferably be based on how long the heater has been running, and how long the heater was shut off (on off and on cycle) after the set temperature has been reached, in the first cycle, and then predict for the next cycle, how long the fan should continue to run based on the data from the previous cycle(s) and preferably the current cycle. So, the fan run time extension is preferably always predicted considering the data from the previous one on-off-on cycle or previous multiple on-off-on cycles.

When the thermostat calls for heat, the thermostat heat or ‘W’ output 225 in FIG. 2. goes typically to 0 vac. This makes the input 116 in FIG. 1 goes to 0 vac as well. The voltage regulator 107 output will create a positive DC voltage at the anode of diode 146, charges up capacitor 161 and create a positive DC voltage at the base of transistor 110. This turns on the transistor 110, and cause input 135 to microprocessor 103 to be at 0 vac or low voltage state. The microprocessor 103 will then make output 133 go to approximately 5 vdc or high voltage state. When output 133 is in high voltage state, transistor 104 turns on, and the regulator's 107 output through resistor 165 activates triac 114 which in turn pulls heater output 125 to 0 vac. Heater output 125 in FIG. 1 is the same connection as output connector 213 of 201 in FIG. 2. Output 125 of FIG. 1 is therefore connected to heater input ‘W’ 207 of FIG. 2. This turns on the heater 204 of HVAC 200 in FIG. 2. In a HVAC system, if heater is a gas heater, the thermostat will not turn on the fan when there is a call for heat. If the heater is an electric heater or a heat pump, the thermostat will also turn on the fan when there is a call for heat.

Assuming an electric heater, when there is a call for heat, the thermostat fan or “G” output 224 in FIG. 2 goes to 0 Vac. Since 224 of FIG. 2 is connected to 222, which is the same terminal as input 115 of FIG. 1, this makes the input 115 goes to 0 vac as well. This in turn turns on transistor 109, and cause input 136 to microprocessor 103 to be at low voltage state. The microprocessor 103 will then make output 131 go to high voltage state. When 131 is in high voltage state, transistor 106 turns on, and triac 112 is activated. This cause fan output 124 of integrated circuit 100 to go to 0 vac. Fan output 124 of FIG. 1 is the same connection as terminal 214 of FIG. 2, which is connected to 206 and turns on the fan 203 of HVAC 200.

As described above, when there is a call for heat by the thermostat, the input 135 in FIG. 1 goes into a low voltage state. The microprocessor 103 records the duration of input 135 in low voltage state which is the heater ON time. When the room temperature has reached its upper hysteresis set temperature, the thermostat 202 heater output terminal 225 in FIG. 2 goes to 24 vac. This in turn makes input terminal 116 of FIG. 1 goes to 24 vac and turns off transistor 110, and cause input 135 be in high voltage state. The microprocessor 103 then causes its output 133 to low voltage state which turns off the heater. In addition, microprocessor 103 also record the duration of input 135 in high voltage state which is the heater OFF time. The software in the microprocessor 103 stores the data of heater previous cycle(s) ON time (input 135 in low voltage state), and heater previous cycle OFF time (input 135 in high voltage state) and the heater current cycle ON time. Then, at the end of the current heater ON cycle which is the next time this line 135 transitions from low to high voltage, the microprocessor 103 takes the previous cycle's heater ON time and Off time and the current ON time, and computes or predicts how long its output 131 (which controls the fan), should continue to remain at high voltage state to keep the fan ON at the end of current heater ON time.

Since the heater element in the heat exchanger gets to its maximum temperature fairly quickly (e.g., 7 minutes), by the microprocessor measuring the heater ON time it can be determined if the heater has reached its maximum temperature. After the heater elements have shut off, the microprocessor can estimate how much residual energy is left that can still be used to heat up the room, which determines with how much the fan run time should be extended.

In addition, the heater OFF time during the ON-OFF-ON cycle(s) indicates the rate at which the room cools down after the heater is OFF and this depends on the temperature difference between the room and the outside ambient and the environment of the room such as wall insulation, number of living occupants, heat generating appliances (electronic or electrical equipment, lights, computers, TV, etc.), and so on. If the heater OFF time is short, the fan extended run time should also be short as it takes faster for the residual heat energy left at the heat exchanger to cool down as well. This also will prevent cool air from circulating in the room.

As an example, if the room set temperature is 75° F. (75° F.+/−1° F. as hysteresis), and the outside temperature is 60° F., the heater may run for 20 minutes to get the room reached (76° F.). The heater then shuts off for let's say 10 minutes for the room to drop the temperature down to 74° F. and then it turns on again for let's say 15 minutes. From experiments we have conducted it was determined that all furnaces reached their maximum temperature after 7 minutes of burning. The furnace control board will usually let the fan continue to run for 90 seconds after it has shut down. We shall call this the default fan run time extension. So, an exemplary algorithm is to measure if this 7 minutes has been reached, and assign a 1 (one) minute fan extension, if it has been reached. For the 10 min of heater off, a 20% may be assigned as time extension, or 2 min. For the current heater ON time of 15 min (i.e., over 7 min), another 1 minute may be assigned as time extension. So the total fan time extension is 4 (four) minutes in this example. The algorithm can then compare this total time to see if it is above the default extension time of 90 seconds, and if it is, then it will extend the fan run time with an additional 4 minutes minus 90 seconds, or 2.5 minute additional fan run time. In the above example, if the heater was OFF for 6 minutes instead of 10 minutes, then the total fan time extension would be 1 min+1.2 min+1 min, which is 3.2 minutes. In this case, the software will ask the fan to extend for 3.2 min minus 90 seconds, or 1.7 minute additional fan run time.

In addition, to increase the efficiency of the system even further, if the HVAC's heating elements have been operating continuously for a period of time (e.g., 20-30 minutes), they will be made by the ESC to shut down for a short period of time (e.g., 3-5 minutes) with the fan still running, to not only reduce the furnace temperature therefore extending its life, but also harvest some residual heat energy for the conditioned room.

For air conditioning, the same ESC will adjust fan operation automatically for cooling using an algorithm derived from the stored energy left in the water condensed on the cooling coils and the rate at which the room gets heated up, which depends on a number of factors including the room's insulation, number of occupants in the room, number of appliances operating in the room, temperature difference between the room and the outside ambient, etc., after the air conditioner has shut down. The algorithm will preferably be based on how long the compressor has been running, and how long the compressor was shut off (on-off-on) in previous cycle(s). When the thermostat calls for cool, in FIG. 2, thermostat 202 output 226 will go to 0 vac. Since output 226 is connected to terminal 221 of 201 which is the same as input 117 in FIG. 1, the anode of diode 139 has a positive DC voltage from the output of regulator 107, through resistor 138 and charged up the capacitor 144 and turns on transistor 111. This in turn makes input 134 of microprocessor 103 to become low voltage state. Microprocessor 103 in turn will cause its output 132 go to high voltage state. Then, transistor 105 get turned on, and triacs 113 activated. This in turn causes cooling terminal 126 be in 0 vac which make terminal 215 in FIG. 2 go to 0 vac as well. This then turns on the AC compressor 205 of the HVAC 200. Also, when the thermostat calls for cool, the fan output 224 of thermostat 202 is also in 0 vac which cause the fan 203 of HVAC 200 to be turned on as well. The microprocessor 103 records the duration of its input 134 in low voltage state (AC compressor ON) and in high voltage state (AC compressor OFF). Then, at the end of the next compressor ON cycle, the software makes its output 131 which controls the fan, to stay on for a predicted period of time after the end of the compressor ON period. This continues on, cycle after cycle, with the fan extension period based on the data from the previous compressor ON and OFF cycle(s) and current ON cycle. The predicted fan extension run time is computed by the software that uses the data of the previous cycle(s)′ compressor ON, OFF and ON duration (see example below).

For example, based on an average air humidity of 50%, after the compressor has run for 20 minutes, the average AC condenser coil is typically dripping wet. This will be equivalent to maximum latent cooling energy, which is available when the water condensed in the coil is evaporated away. With fan blowing, it takes typically approximately 5 to 7 minutes to evaporate the water to dry with a 50% air humidity. So, by measuring how long the compressor is ON and assuming an average of 50% humidity for example, the ESC can extrapolate the estimated the available energy, and thus, how long the fan run extension should be, from the partially wet condenser coils if the AC is ON for less than 20 mins. For example, if the compressor has run for 10 minutes and the air humidity is 50%, the fun extension time may be 3 minutes. With the data on how long the AC compressor was OFF before it kicks on again, ESC can adjust this fan extension time further (see example below). It should be noted that this is for the situation when the compressor is ON for less than preferably 30 minutes continuously. If the compressor was ON for preferably 30 minutes, the microprocessor will shut down the compressor regardless if the room temperature has been reached or not, but keep the fan running for the next cycle.

Again, by monitoring the compressor ON time and compressor OFF time, the ESC also obtains an indication of the difference between the room temperature and the outside air temperature and the rate at which the room is heating up after the compressor is OFF.

For example, if the outside temperature is 100 degrees Fahrenheit (° F.) and the room set temperature is 75 degrees F. (assume a hysteresis of +/−1 degrees ° F.), the compressor could be running for 20 minutes before the room reached the 74 degrees F. (75° F.−1° F. hysteresis) and then the compressor goes to OFF maybe for 5 minutes. After the compressor is OFF, then the room will get heated up relatively fast due to 100 degrees F. outside. So, when the room temperature gets to 76 degrees F. (75° F.+1° F. hysteresis), the compressor is ON again and let's assume for 10 minutes before it reaches the set temperature again. The fan time extension algorithm may be to take 10% of previous ON period, which is 2 minutes (“mins”), plus 20% of the previous OFF period, which is 1 min, plus 20% of the current ON period which is 2 mins totaling 5 mins, which would mean to extend the fan run for 5 mins at the end of the current compressor ON time. However, if the outside temperature is only 85 degrees F., then, it takes longer for the room to be heated up to 76 degrees F. In this case, the compressor OFF time is maybe 7 minutes; and let's assume the compressor is ON again for 10 mins after that. So, the algorithm for fan extension at the end of this current 10 min compressor ON time may be 2 min plus 1.4 min plus 2 min which total 5.4 minutes. So, by measuring the compressor ON time, and compressor OFF time, the ESC can estimate the temperature difference between outside air and room air, and the rate at which the room gets heated up after the compressor is OFF from other temperature changing activities in the room, thus, how long the fan extension run time should be. Thus, shorter fun extension run times will apply when the difference between the room temperature and the outside air temperature is greater, and vice versa.

If the HVAC's cooling elements have been operating continuously for a period of time (e.g., 20-30 minutes), they will be made by the ESC to shut down for a short period of time with the fan still running (e.g., 3-5 minutes) to harness the stored energy left in the water condensed on the cooling coil.

Hence, the ESC recovers and delivers more heating and cooling energy to the conditioned space than is possible with original controls from the thermostat. The ESC improves the efficiency of HVAC equipment by delivering additional heating or cooling capacity for a small amount of additional electric energy (kWh) utilized by the fan.

Air conditioners cool conditioned spaces by removing sensible and latent heat from the return air which reduces the supply air temperature and humidity. Latent heat is removed as water vapor is condensed out of the air due to the temperature of the evaporator coil being less than the return air dew point temperature. Latent heat is the quantity of heat absorbed or released by air undergoing a change of state, such as water vapor condensing out of the air as water onto a cold evaporator coil or cold water evaporating to water vapor which will cool the air.

Most evaporators are cold and wet (below 40 to 50° F.) after the compressor turns off. Cooling energy left on the evaporator coil after the compressor turns off is generally wasted. The evaporator absorbs heat from its surroundings and cold water on the coil flows down the condensate drain.

Again, the ESC as disclosed herein, recovers the remaining cooling energy from evaporator coil by operating the fan after the compressor turns off to cool the conditioned space. In addition, after the compressor has been running for a period of for example approximately 20-30 minutes, the evaporative coil is cold and wet, and by shutting down the compressor while keeping the fan running for, for example, 3-5 minutes, the water evaporating away at the evaporative coil cools down the incoming air flow from the ducting.

Again, most furnace heat exchangers are still hot (above 135 to 210° F.) after the furnace fan turns off. The ESC recovers the remaining heat energy from the hot furnace heat exchanger after the furnace turns off and delivers this heat to the conditioned space. In addition, after the heating element has been running for a period of for example approximately 20-30 minutes, the hot heat exchanger is at its maximum temperature, and by shutting down the heating element while keeping the fan running for, for example 3-5 minutes, the residual heat energy still heats up the incoming air flow from the ducting.

Again, as described earlier when referring to FIG. 2, the ESC works by preferably disconnecting from the original thermostat, all the original wires that come from the air handler unit, and re-connecting all these wires to the ESC module. A set of duplicate wires from the ESC is then directly connected to the thermostat (see FIG. 2). As shown in FIG. 2, the ESC 201 may have five wires (green, white, yellow, common and red) to be connected to the thermostat after disconnecting from the thermostat the corresponding five wires that come from the air handler unit control board (258 in FIG. 2a ), which will then be connected to terminals 213-217 of the ESC 201 as shown in FIG. 2. In another exemplary embodiment, the ESC 201 may have six wires as shown in FIG. 2a . The sixth wire may be, as shown, a pass-through wire 245 and may be used for example to connect the thermostat's reversing valve O/B output to the air handler control board 258.

It should be noted that providing the same number of wires and wires that have identical color coding as the original wires that come from the air handler control board 258 comes with the advantage of eliminating or minimizing mistakes during installation by the field technicians.

When the thermostat sends out to the fan, compressor and heater signals, they now all go to the ESC. If not a pass-through wire, the ESC reads the signals from these wires coming from the thermostat and automatically sends out the desired signals described herein to the air handler unit control 258 that controls the HVAC.

Again, the ESC may use the outputs of the thermostat as its inputs. The command signal from the thermostat may be either a high of 24 vac or 0 vac (ground) or sometimes in floating state. Correspondingly, the ESC is configured to accept either 24 vac or 0 Vac or float state as its inputs so that it can interface with every manufacturer's thermostats used in HVAC systems.

In another embodiment, a temperature sensor (not shown) can be installed in association with the ESC to sense the temperature of the outside air. The ESC can be installed inside the house next to the thermostat, or at the air handler in the garage or attic or outside the building on the roof for roof top units (RTU). If the ESC is installed inside the house, a remote temperature probe can be installed outside the house and sending the information to the ESC by RF signal. The purpose of this temperature sensor will be described hereinafter.

Alternative ways of installation or integration of the ESC 201 may be provided as in the examples shown in FIGS. 3-4. Again, FIG. 3 is a block diagram illustrating that the ESC 201 can be part of the air handler control board 258 as an add-on circuitry or being integrated into the control board 258 circuitry or logic. FIG. 4 is a block diagram illustrating that in another alternative, the ESC 201 can be part of the thermostat as an add-on circuitry inside the thermostat or being integrated into the circuitry or logic of the thermostat. In other words, a thermostat 202 (FIG. 4) may be provided having the functionality and the benefits of the ESC as described in this disclosure.

In yet another embodiment, the reversing valve signal from the thermostat may be read by the ESC. The reversing valve is identified as O/B terminal on the thermostat. In FIG. 2, the input terminals 212 will have an additional terminal (shown in FIG. 2 as unconnected terminal) to connect to the thermostat's reversing valve O/B output (not shown in FIG. 2). The ESC can read this output to do the following functionality. For heat pump HVAC system, the compressor is used in reverse to provide heat to the rooms. In this case, the ESC will read the reversing valve output (O/B) from the thermostat, and will preferably either disable the extend fan run time, or extend the fan run time to for example 25% of its programmed duration after the heat pump (compressor) has completed its cycle. For example, if the outside temperature is below 40 degrees Celsius (C), the additional fan run time or the compressor shut down with fan running may bring in very cold air. Therefore it would be desirable to install a temperature sensor in association with the ESC to bypass the energy saving features described earlier in this disclosure if the outside temperature is sensed to be below a predetermined level (e.g., 40 degrees C.).

Also, preferably, for the heat pump mode, the ESC will not shut down the heat pump (compressor) for a few minutes after a continuous run of for example 20-30 minutes, to ensure no cold air is blowing into the room.

In another embodiment, a humidity sensor can be installed in association with the ESC to sense the humidity of the outside air if the ESC is installed at the roof top, or the inside room air if the ESC is installed inside the building. During the summer, in some months and some parts of the country, the humidity could be for example over 75 percent. Since the energy saving feature of the ESC is based on the recovery of latent energy from evaporating away the water condensed onto the cooling coil, when the humidity is very high, the condensed water cannot be evaporated away. In addition, blowing high humidity air into the room with the compressor off is uncomfortable for many people. Therefore it would be desirable to install a humidity sensor in the ESC to bypass the energy saving features if the outside humidity is for example over 75% or the inside humidity is over for example 65%. This bypass feature can be factory programmed or user programmed depending on the user's choice.

The apparatus and methods disclosed herein are suitable for split type central HVAC's or independent heater and compressor systems.

As it will be described in more details below, in another embodiment, a new plug and play energy saving controller (ESC/EFC) may be configured to provides a wireless (e.g., Wi-Fi) enabled circuit device for open automated demand response capability, thus eliminating the cumbersome, challenging and/or expensive task of replacing the entire thermostat, while still accomplishing the goal of the DR/ADR approach to save energy. While the description that follows emphasizes Wi-Fi, and the names used for the controller predominantly include the Wi-Fi term, it should be apparent that similarly other wireless communication protocols may be employed (e.g., Bluetooth™, RF, Zigbee™, etc.) instead of Wi-Fi.

In another embodiment, in addition to providing a wireless (e.g., Wi-Fi) enabled circuit device for open automated demand response capability, the new plug and play energy saving controller may be configured to provide a circuitry, such as described within this disclosure, for ensuring energy efficient operation of the HVAC system outside of a demand response occurrence, thus further saving energy.

In an example, a wireless (e.g., Wi-Fi) enabled automatic demand response (ADR) efficient fan controller (EFC) (or energy saving controller (ESC)) may also extend the fan run time after the heating or cooling unit has shut off, and may provide also compressor rest if the compressor has been running continuously for a period of time. More specifically, as an example, the controller may be a Wi-Fi enabled efficient fan controller device with firmware algorithms to read commands from a secured URL site, and write the status of the EFC and thermostat outputs to another secured URL website, and have the EFC execute on the commands in accordance to the read commands.

Advantageously, the Wi-Fi EFC device that can be connected between an existing thermostat and the air handler of an HVAC system, so that the automated demand response can be implemented without having the need to replace the thermostat.

In addition, as described herein, the Wi-Fi EFC device may also provide blower fan extension to save energy during regular operations outside of a demand response occurrence. The blower fan will automatically be extended based on for example how long the air conditioning compressor has been running and how long the compressor has been off.

For the heating, the blower fan may also automatically be extended based on for example gas valve activation time or furnace operating time or Heat Pump activation time and how long the heating elements were off.

In an example, the amount of time the fan continues to operate after the heating element is off or after the air conditioner compressor is off, varies with the amount of time the heating element or compressor are on, and the amount of time the heating element or compressor are off, over many cycles by using microprocessors and firm wares, as described herein. The heating element additional fan run time relates to how much left over heat is stored in the heat exchanger. The air conditioner compressor additional run time relates to how much cold water is condensed on the evaporator coil.

Hence, the Wi-Fi EFC recovers and delivers more heating and cooling energy to the conditioned space than is possible with original HVAC fan controllers. The Wi-Fi EFC improves the efficiency of HVAC equipment by delivering additional heating or cooling capacity for a small amount of additional electric energy (kWh).

Again, for the Wi-Fi EFC to work universally, it has to interface with every manufacturers of thermostats used in HVAC system. There are many manufacturers of thermostats where the fan output command signal goes into a floating or unknown state when the thermostat is shut off by putting the thermostat switch to system off.

In such a case, if an EFC is connected to the thermostat, the fan command signal being in unknown state could be read in as ON state, and the EFC will turn the fan on and run continuously.

Therefore, as described herein, the Wi-Fi EFC circuitry may be configured to read any unknown or floating signals from the thermostat fan command signal as known 24 vac or 0 vac state. In this way, the fan will always be turned off when it is at not at an ON state.

FIG. 5 is a flow chart illustrating an exemplary process flow of a wireless energy saving controller, according to another embodiment. The exemplary process flow shown in FIG. I 5 regards the turning off of a compressor or a compressor and fan for a duration of time, such as 6 minutes 588-587 or 12 minutes 586, for example. It should be noted that the process flow illustrated by FIG. 5 is disclosed in greater detail hereinafter when referring to FIGS. 6a -b.

FIG. 6a-b are block diagrams of an HVAC system incorporating a wireless energy saving controller (“WIFI ESC”), as disclosed hereinafter, according to another embodiment. As an example, the WIFI ESC of FIG. 6a may be a wireless energy fan controller (“WIFI EFC”) 601 w, as disclosed hereinbefore. The WIFI ESC of FIG. 6b may be an MVDR 601, as disclosed hereinafter when referring to FIGS. 7-11, for example. It should be noted that, hereinafter when referring to FIGS. 6a-b , the terms wireless energy saving controller, Wi-Fi integrated circuit device, integrated circuit, or WIFI ESC refers to both a WIFI EFC 601 w and an MVDR 601.

As shown in FIG. 6a , the WIFI ESC circuit device 601 w, 601 may have an input port 612 w, 612 having a plurality of input terminals and an output port 611 w, 611 having a plurality of output terminals for connecting the Wi-Fi ESC 601 w,601 with the thermostat 602 and the HVAC system 600. In an example, the plurality of input terminals includes six (6) input terminals, plus a temperature probe 672, on one side of the device. The temperature probe 672 is an input to measure the temperature of the conditioned space, for example. The plurality of output terminals includes the matching six (6) output terminals located on the other side of the device.

As shown in FIGS. 6a-b , the six input terminals 612 w, 612 may be flying wire leads and may be connected to the thermostat's terminals for Common [C], Power (RH/RC), Fan (G), Compressor (Y), Heat (W), and Reversing Valve (O/B).

The six output terminals 611 w, 611 may be either flying leads or terminals blocks similar to the terminal blocks of a regular thermostat. As shown in FIG. 6a-b , the six outputs are connected to the wires bundle coming from the HVAC air handler unit.

The WIFI ESC 601 w, 601 may be installed at the back of the thermostat inside the drywall, for example. It should be apparent that the Wi-Fi antenna 671 and temperature prove 672 of the integrated circuit 601 w, 601 should not be covered during installation with any potting material, for example. The temperature probe 672 may typically stick out through a small opening in the drywall, and may also be position close to the thermostat 602, such that the temperature probe 672 can measure a temperature that is close to what the temperature probe of the thermostat 602 is measuring.

By having the same sets of inputs and outputs, as shown in FIG. 6a-b , the Wi-Fi ESC device 601 w, 601 can be connected directly to the thermostat terminal, thus making the installation easy. Further, the thermostat terminals' connectors are usually designed for a single wire. By using the Wi-Fi ESC device, only the wires from Wi-Fi ESC are connected to the thermostat, and thus, there are no multiple wires into a same terminal that can create connection reliability issues.

The Wi-Fi ESC circuit 601 w, 601 may have a microprocessor with Wi-Fi module 671A the configuration and function of which are well known in the art. The Wi-Fi module 671A may be configured to communicate via a Wi-Fi antenna 671 and a wireless router 673 in the building connected to the Internet, with an external network 674 (e.g., a network of the utility provider).

The Wi-Fi EFC 601 w of FIG. 6a can perform the multitasking associated with the processes described herein, using RTOS (Real Time Operating System) as known in the art. In an example, the device 601 w (501 w in FIG. 5), on a regular interval (e.g., every 10 seconds), may be configured to read (step 581) instruction set(s) from a specific secured URL site of the external network 674, which, for the purpose of this description will be called as “Read URL”. The READ URL may be managed by the Utility provider based on Open ADR specifications or a private set of specifications. If there is no instruction for it, the Wi-Fi EFC 501 w does nothing (step 583). If there is an instruction for it (e.g., a demand response request, step 582), in an HVAC cooling mode, the Wi-Fi EFC 501 w may be programmed to for example check the room temperature (step 584) and if the room temperature is not greater than a set level (e.g., 80 degrees Fahrenheit), execute the instruction. The instruction may be for example to turn compressor off for six minutes (step 588), to turn compressor and fan off for six minutes (step 587), to turn compressor and fan off for twelve minutes (step 586), or the like.

The Utility provider network 674 may also provide another secure network URL site, which, for the purpose of this description will be called “WRITE URL”. This WRITE URL may also be managed by the Utility provider based on Open ADR specifications or a private set of specifications.

After the execution of the instruction, Wi-Fi EFC 501 w may be programmed to report to the WRITE URL (step 591) that the instruction was executed (step 589) and also the status of the HVAC (step 590; e.g., compressor is off).

As shown in FIG. 5, the Wi-Fi EFC 501 w may also be programmed to periodically (e.g., every 10 seconds) report to the WRITE URL the status of the HVAC system (steps 592-593).

Sometimes, the Wi-Fi EFC 501 w may get a false command while reading the READ URL command lines. At other times, there may be inconsistencies in the string of commands in the READ URL as provided by the Utility network. In such a case, the Wi-Fi EFC 501 w, after checking whether the room temperature is above a set point (step/event 584), will look for the next command line to see whether it should follow step/event 588, or event 587 or event 586. If all the 3 possible events are negative, then Wi-Fi EFC 501 w will go to False Demand Response event 585 and will go to DO NOTHING event 583.

For example, the READ URL may consist of multiple command lines. The first command line may say there is a Demand Response Event (582). The second command may say Turn Compressor and Fan off for 6 mins (587). The third command line may say write status of HVAC (592) right away, etc. However, if READ URL 581 says Demand Response Event (582) is occurring, but the second command line did not specify to execute 588 or 587 or 586, or ask it to execute some unknown commands, then this is considered as a False Demand Response Event 585 and the Wi-Fi EFC 501 w will do nothing 583.

It is important to note that in an example the Utility provider network 674 does not access the Wi-Fi EFC device at all. It only posts the command/instruction sets it wants executed by a specific Wi-Fi EFC device that corresponds to the serial number, MAC address and encryption key posted in the READ URL. When a matching Wi-Fi EFC sees the commands, it downloads these commands and together with the temperature reading from the temperature probe, may be configured to make exemplary decisions as follows: A) to shut down the compressor (or heater) only for short period of say, 3 minutes to 12 minutes, B) shut down the compressor (or heater) and fan for a short period of time, say 3 minutes to 12 minutes or C) Do nothing, i.e., keep the compressor (or heater) and fan in its current state whether they are off or running.

Similarly, the MVDR 601 of FIG. 6b can perform the multitasking associated with the processes described herein, using RTOS (Real Time Operating System) as known in the art. In an example, the device 601 on a regular interval (e.g., every 10 seconds), may be configured to read instruction set(s) from a specific secured URL site of the external network 674, which, for the purpose of this description will be called as “Read URL”. The READ URL may be managed by the Utility provider based on Open ADR specifications or a private set of specifications. If there is no instruction for it, the MVDR 501 does nothing. If there is an instruction for it (e.g., a demand response request), in an HVAC cooling mode, the MVDR 501 may be programmed to for example check the room temperature and if the room temperature is not greater than a set level (e.g., 80 degrees Fahrenheit), execute the instruction. This room temperature could be programmed by the user or operator. The instruction may be for example to turn compressor off for a duration of time, to turn compressor and fan off for another duration of time or the like.

The Utility provider network 674 or a remote server 415 of FIG. 4 may also provide another secure network URL site, which, for the purpose of this description will be called “WRITE URL”. This WRITE URL may also be managed by the Utility provider based on Open ADR specifications or a private set of specifications.

After the execution of the instruction, MVDR 601 may be programmed to report to the WRITE URL that the instruction was executed and also the status of the HVAC (e.g., compressor is off).

The Wi-Fi MVDR 601 may also be programmed to periodically (e.g., every 10 seconds) report to the WRITE URL the status of the HVAC system.

Sometimes, the MVDR 601 may get a false command while reading the READ URL command lines. At other times, there may be inconsistencies in the string of commands in the READ URL as provided by the Utility network. In such a case, the MVDR 601, after checking whether the room temperature is above a set point, will look for the next command line to see whether it should follow step. If all possible events are negative, then MVDR 601 will go to False Demand Response and will go to DO NOTHING.

For example, the READ URL may consist of multiple command lines. The first command line may say there is a Demand Response Event The second command may say Turn Compressor and Fan off for a period of time. The third command line may say write status of HVAC right away, etc. However, if READ URL says Demand Response Event is occurring, but the second command line did not specify to execute an event, or ask it to execute some unknown commands, then this is considered as a False Demand Response Event and the MVDR 601 will do nothing.

It is important to note that in an example the Utility provider network 674 does not access the MVDR device at all. It only posts the command/instruction sets it wants executed by a specific MVDR device that corresponds to the serial number, MAC address and encryption key posted in the READ URL. When a matching MVDR sees the commands, it downloads these commands and together with the temperature reading from the temperature probe, may be configured to make exemplary decisions as follows: A) to shut down the compressor (or heater) only for short period of say, 3 minutes to 12 minutes, B) shut down the compressor (or heater) and fan for a short period of time, say 3 minutes to 12 minutes or C) Do nothing, i.e., keep the compressor (or heater) and fan in its current state whether they are off or running.

In an example, all the Wi-Fi ESC 601 w, 601 in the ADR network will be configured to access the READ URL at periodic intervals, say every 10 seconds.

There may be multiple WRITE URL sites, posted in the READ URL site, depending on for example the commands set. For example, the READ URL may ask the Wi-Fi ESC 601 w, 601 to write the status of the compressor whether it is currently on or off, whether the fan is currently on or off, the temperature of its temperature probe 672 and/or its serial number to a first WRITE URL. Further, it may ask the Wi-Fi ESC 601 w, 601 to write to a second WRITE URL to report its MAC address, encryption key, the current time, delays in staging, etc. So, there may be many WRITE URLs so that the READ URL may ask the Wi-Fi ESC 601 w, 601 to post to for various aspects of reporting, so as to enable the Utility providers to implement the Open ADR efficiently.

Again, it is important to note that using the above described (READ/WRITE URL) configuration, the Utility provider network does not have unauthorized access to the Wi-Fi EFC device 601 w, so that privacy concerns are minimized. Again, the Wi-Fi ESC 601 w, 601 will read instructions from the READ URL. The secured WRITE URL will only accept data in a specialized format to be written or posted to it. The data to be written to the WRITE URL are based on what the REAL URL command sets requires the Wi-Fi ESC 601 w, 601 to perform.

The sets of commands in the READ URL could be how often the Wi-Fi EFC should reads from the READ URL, how often and what information it should write to the first WRITE URL, when and what information to write to the second WRITE URL, how and what to write to the third WRITE URL etc.

The READ URL may have many thousands of sets of instructions and each set of instructions may have a unique serial number, MAC address and/or encryption keys so that only the matching Wi-Fi ESC 601 w, 601 reads its own command set. This is because there may be many thousands of Wi-Fi ESCs accessing the same READ URL at the same time. In this way, the Utility provider can select which Wi-Fi ESC 601 w, 601 to instruct it to shut down the compressor (or heater) and/or blower fan or only the compressor, at what time frame, etc.

Again, the Wi-Fi ESC 601 w, 601 may be connected in series between the thermostat 602 and the HVAC air handler unit control board 658. All the wires from the thermostat go into the Wi-Fi ESC device 601 w, 601, and the Wi-Fi ESC's microprocessor controls as described herein the relays and switches of the air handler controller, to bypass the connection with the thermostat outputs (compressor, fan and heater) and manipulates the connections to turn the compressor on and off, the fan on and off and the heater on and off.

Once the Wi-Fi ESC 601 w, 601 reads a command sets corresponding for example to its serial number, MAC address and encryption key, and the instruction sets contains a shut compressor down event, the Wi-Fi ESC 601 w, 601 will break the wires coming from the thermostat to the air handler unit controller 658. In this way, even though the thermostat may still be requesting for cool and the thermostat outputs sends a call for compressor be turned on, the Wi-Fi ESC device will intercept that wire and shuts the compressor down.

In this way, the Utility provider is able to cause the homeowner compressor to shut off without needing to access the thermostat as it is currently being done to implement the automatic demand response to prevent brownouts and blackouts.

FIG. 7 is a flow chart illustrating the hardware and firmware architecture of a WiFi or wireless enabled MVDR, according to an aspect.

As mentioned hereinbefore, an HVAC system may be equipped with a WIFI enabled energy saving controller. As an example, the WIFI ESC may be a WIFI enabled device which also determines and reports the quantity of energy saved via a real time measurement and verification system and a demand response capability (“MVDR”), and which may also be configured to act as an energy saving controller. More particularly, an MVDR may be a WIFI enabled device which may perform Open Automated Demand Response (OpenADR), as defined by the utility provider, provide measurement and verification (M&V) of the performance of energy savings devices in real time, and have the ability to further do one or more of the following:

i) to calculate the energy savings from data collected in real time via the WIFI or wireless communication of equipment connected to the MVDR, ii) to measure and verify in real time, the actual energy savings performance of an energy saving devices connected to an HVAC system by data logging and streaming said data to a cloud server, the ON and OFF status of the blower fan, of the compressor and of the heater, iii) to measure and verify in real time, the actual blower fan run time extension of HVAC systems after the heating or cooling unit has shut off, iv) to measure and verify in real time, the actual compressor rest run time and stop time, v) to measure and verify in real time, the actual temperature, humidity, and pressure of the supply and return air at the air handler unit inside the ducts, vi) to measure and verify in real time, the actual temperature, pressure and humidity of the refrigerant lines of the compressor in an HVAC system vii) to measure and verify in real time the actual supply and return temperature and/or pressure of the refrigerant lines of a refrigeration unit such as a freezer, refrigerator, fridge, cooler or chiller viii) to measure and verify in real time, the actual energy consumed in regular intervals by measuring the current or amperage draw of the power lines to a lighting system, etc. ix) to turn energy consuming equipment on or off or to modify its operating behavior via the internet or wireless communication.

It should be noted that the following description is a description for the exemplary flow chart illustrating the hardware and firmware architecture of a WiFi or wireless enabled MVDR as shown in FIG. 7.

Applying power to an MVDR starts the processes it performs 700, as disclosed hereinbefore. First, the device goes through a self-diagnostics test process 701. In the self-diagnostics test 701, the microcontroller checks for faults, valid inputs from connecting equipment, valid sensors values, etc., and then activates watchdog 702. A watchdog may be a device used to protect a system from software or hardware failures, as is known to those of ordinary skill in the art. Once the self-diagnostics 701 are completed, the MVDR waits for an operator to do the Provisioning 703. During the provisioning process 703, the MVDR connects to a remote server, which could be for example a cloud based or local stand-alone server. Next, the MVDR fetches the first set of read instructions from the remote server 704, which may be settings instructions, for example. After the MVDR accesses the remote server to retrieve settings instructions 704, the remote server records that as a read function, and displays the instructions on the read screen of the web interface. The MVDR then performs whatever tasks are contained in the read instructions 705.

If the first read 714 is not successful, the operator will not see the read instructions 704 on the web interface, and therefore the operator knows the provisioning 703 was not successful. The operator will then need to do power reset 706 and start over. It should be noted that FIG. 9 illustrates more details on the provisioning 703 process.

If the first read 714 is successful, then the watch dog timer starts up automatically 707. After that, data begins to stream from the MVDR to the remote cloud server 708, which can then be viewed on the web interface 713. The frequency of this data streaming will depend on the settings instructions 704. Finally, the data streamed from the MVDR gets written into the data base of the cloud server 709.

In an example, the streaming rate is a variable that the end user or the utility provider or a data aggregator hired by the utility provider for example can set via a user interface, which may be provided via a website. The streaming rate could range from 1 sec to 1 hour for example depending on for example the energy consuming equipment/devices monitored. This is called the streaming rate (or sampling rate). Some devices do not need high streaming rate, which will save the website storage space. Other device may need high streaming rate.

For example, for HVAC, it is not necessary to stream the data every 1 (one) second. Usually it is at 30 secs since the monitoring is for 24 hours 7 days a week, which can accumulate lots of data, especially if there are hundreds of thousands of installation.

In an example, the MVDR hardware may be configured to do its own energy saving calculations, which can be more accurate since the MVDR can detect exactly for example when the energy consuming equipment is on or off or the exact time when the state of the energy consuming equipment changes. The energy saving calculations may include for example adding all the amounts of energy consumed by the energy consuming equipment during the ON states of the equipment in a day (24 hours). The raw or calculated data may be also streamed to the server and the server can perform its own calculations. The server can also compare the MVDR calculated data versus its own energy saving calculation and use any errors to compensate for accuracy.

As an example for HVAC, let's say the stream rate is 30 secs (i.e., t, t+30, t+60, t+90, etc.), where “t” is the time when the stream starts and let's say that at that time the compressor is OFF. Let say at time t+5, the compressor turns ON. The MVDR will capture this info as follows:

t: compressor OFF

t+30: compressor ON

But actually, the compressor starts at t+5. So, the server data will have the sampling error of 25 sec, whereas the MVDR will start the energy usage calculation at this t+5 until the compressor shuts off again.

In another example, the MDVR may be configured to send a report to the server every time the compressor change state, in addition to the regular streaming rate. So, there is some data duplications to verify that the energy savings data capture is correct for the user.

Simultaneously, the watchdog 707 waits to get “petted,” i.e., waits for a periodic read, and will monitor if the MVDR's periodic read or write access to the remote server 711 is successful. If periodic read 711 is detected, the watchdog timer resets and allows the data streaming to be acknowledged by the cloud server 713. If periodic read 711 is not detected or not successful, the watchdog will wait, for example, 9 hours. If in 9 hours 712 the periodic read is still not successful, then the watchdog will execute a hardware reset as process 710. This will clear any faults or errors due to WiFi connectivity and resets the MVDR hardware with the WiFi module to re-connect back to the server.

FIG. 8 illustrates the functional block diagram of the hardware of the MVDR, according to an aspect. Inputs 801 are connected 801 a to the equipment to be monitored and controlled. As shown, some of these inputs 801 can be directly connected to the outputs 802 (i.e., pass-through input signals). These may be input signals that are not being used by the MVDR, but which need to be at the outputs that re-connect back to the equipment. A reset button 803 may initiate a hardware hard reset or power reset to clear any faults in the MVDR hardware without turning the power off and may be controlled via a user initiated action. The power supply 804 may convert the input AC power, such as single phase 24 Vac, 110 Vac, 220/240 Vac, 3 phase 208 Vac, or 3 phase 480 Vac, into suitable working DC voltages, such as 12 Vdc, 5 Vdc, and 3.3 Vdc which provide power to the microcontroller 206, driver circuits 215, and relays 216, respectively, for example.

As shown in FIG. 8, the input signals 801 taken from the installed energy consuming equipment or from Third Party Device (energy saving equipment) are conditioned 805, such that the input signals 201 can then be input into the microcontroller 806. The microcontroller 806 may have a WiFi module and WiFi antenna, which enable the microcontroller 806 to transmit and receive data from a remote server, as disclosed hereinbefore when referring to FIG. 7. The microcontroller 806 also receives information from many sensors and probes simultaneously, as disclosed hereinafter, for example.

Temperature probes 807 may comprise one or more temperature sensors which measure the temperature at various temperature sensitive locations of the energy consuming equipment, such as supply (liquid line) and return (suction line) of the compressor refrigerant lines, the supply and return air inside the ducts at the air handler unit of a HVAC system, ambient temperature, etc. Pressure probes 808 may comprise one or more probes which measure ambient pressure 811, differential pressures 812, or static pressure 813 at various locations, such as inside an enclosure or inside a HVAC ducting system. Humidity probes 809 may comprise one or more probes which measure the humidity of the air flow inside an HVAC ducts, ambient humidity, and humidity at other various locations in energy consuming equipment or at various locations of the Third Party Device, for example. Power Factor sensors 810 may measure the power factor of the energy consuming equipment or the Third Party Device, and show the lead or lag of the voltage and current waveform to determine if the equipment is capacitive or inductive, for example. Current sensors 811 may comprise one or more current transformers 812 in 50/60 Hz application to measure the current or amperage draw of a power line connected to the energy consuming equipment or Third Party Device. Voltage sensor 813 may comprise one or more voltage measuring circuits which could have a plurality of differential operational amplifiers (OpAmps) 814 which measure the voltage across the power lines that feeds the energy consuming equipment or Third Party Device.

The Microcontroller's 806 outputs go to the driver circuit 815 which drives the series of relays 816. A plurality of relays 816 can be controlled and managed by the Microcontroller 806 via multiplexing. The outputs of the relays 816 go to output 802 of the MVDR. The antenna of the WiFi component of Microcontroller 806 transmits and receives data to the remote server on a continuous basis and these data logs the performance of the energy consuming equipment and/or the Third Party Device to a remote server which becomes accessible through the web interface. In this way, the operator on the web interface can gives commands to the MVDR to perform specific tasks such as turning equipment on and off, changing the speed of motors, changing temperature and pressure or humidity settings, etc.

FIG. 9 illustrates a flow chart detailing an exemplary method for a user to interface between the MVDR hardware and the remote server, according to an aspect. It should be understood that the following is an exemplary description of the user flow chart.

The first step is to register the MVDR with the remote server 900. Registering the MVDR can be accomplished by logging into the cloud server 901, such as http://clicksay.com for example, with the assigned user name and password. After logging in, a user selects Device Management 902 on the menu bar. Then, to add a new device, a user selects the “Add New” icon 903. Once the screen opens up on Add New device, a user fills in the MVDR device ID, Serial Number, MAC address which are the mandatory fields to properly register the MVDR device 904. On the same page, other fields such as amps, volts, single or 3 phase, power factor, cost per KwH can be extracted by the MVDR through one or more of its sensors or can be manually inputted by the operator or user. Select Save 905 to save the entries.

The next step after registration process 900, is the provisioning process 906. To do this, press the provisioning button on the MVDR board for 2 to 3 seconds 907. Then, look for the access point (“AP”) on any WiFi device 918, such as the mobile phone, or iPad or lap top with the wireless access enabled. If the AP is not showing up in the WiFi device, do power cycle 908, and start again by pressing the provision button 907. If the AP is visible from the WiFi device, a user connects to the AP 909. Then, a user opens a browser 910 by typing in the address 192.168.9.2 (from the internet assigned number authority). Next, a user fills up the SSID, Password, and Serial Number assigned to a particular MVDR 911 and save the information 912.

Once the information is saves, the user logs into the remote cloud server (e.g., https://clicksay.com) 913. On the icon, the user selects Settings icon found under the Device Manager list of devices and the user fills in the settings or the instructions to the MVDR 914. As an example, on the Dashboard, Device Management, Device Assignment, Device Search, Device Migration, Demand Response settings, etc all can be selected to manage the MVDRs installed in the field. As another example, on the menu bar one can select User Management in 915 to manage the various levels of user management such as Aggregator Management, Installer Management, Technician Management, Customer Management, etc. Different user levels can be created during step 915. On the menu bar, a user can also select Demand Response or Energy Savings 916. During step 916, energy savings from demand response activities (Energy Savings DR) and energy savings from energy efficiencies implementation of the Third Party Device and processes corresponding to a particular MVDR device ID are displayed to the user. Additionally, a user can select to view the performance and status data of the energy consuming equipment or the Third Party Device being streamed by the MVDR to the remote server accessible from any web browser 917 corresponding to a particular MVDR device ID.

FIGS. 10a-b illustrate exemplary installs of a plurality of MVDRs on an HVAC air handler unit 1000 and an HVAC compressor 1008, according to an aspect. As shown, MVDR1 1001 is installed at the air handler unit with probes 1002, 1003 and 1004. Probes 1002 are inserted into the return air of the HVAC ducting as it returns back to the air handler unit 1000, such that the probes 1002 measure the environment of the air inside the return air duct. Examples of measurements taken regarding the environment of the air inside the return air duct include the static pressure, air temperature, humidity, etc. Probes 1003 are inserted into the supply air of the HVAC ducting, such that the probes 2003 measure the environment of the air inside the supply air ducting as the air leaves the air handler unit to condition a room. Examples of measurements taken regarding the environment of the air inside the supply air duct include the static pressure, air temperature, humidity, etc. Probe 1004 measures the ambient conditions for the atmospheric pressure, temperature, humidity, etc. as the reference base lines, for example. The MVDR1 1001 may send this data to the remote server at a rate or frequency, which the user may set in the settings (step 914 of FIG. 9), to take the measurements and verifications of the performance of an HVAC system.

As an example, a second MVDR (“MVDR2”) 1005 could be installed in the same HVAC system, such that it is installed between the air handler unit control board of 1000 and the thermostat 1007. A suitable installation location may be behind the thermostat 1007 inside the drywall or may be an enclosure mounted next to the thermostat, for example. MVDR2 1005 could take over the existing thermostat's 1007 functionality or could complement the existing thermostat's 1007 function. A probe 1006 connected to the MVDR2 1005 may be placed such that the probe 1006 measures for example the temperature and the humidity of the conditioned room, independent of the sensors from the thermostat 1007. MVDR2 1005 may perform the demand response, set the schedules to be controlled remotely, and/or set the temperature, similar to a typical WiFi thermostat. Additionally, the MVDR2 1005 or MVDR3, MVDR 4, etc, may also calculate the energy saved and stream that information in real time to a remote server 1015 of FIG. 10b , which may then record the measurement and verify of the performance of any Third Party Devices. Thus, instead of depending on the deemed savings calculated by the Third Party Devices, energy savings can be determined and verified by using the MVDR 1005.

The verification may be done by comparing the calculated energy savings based on real-time measurements with deemed energy savings. The server may be configured to perform the comparison automatically or the comparison may be done manually (visual inspection).

In an example, if the HVAC manufacturer states that the optimal run time for each compressor ON cycle is 15 minutes, but the streamed data shows the average compressor ON run time is 25 mins for example, then the user knows that the compressor is undersized or that the compressor is not running optimally and is wasting energy, or needs a tune up, etc.

As shown in FIG. 10b , MVDR3 1009 may be installed at the HVAC compressor/condenser unit 1008, which may be on a roof top or as a standalone unit installed in the back yard of a building, for example. Probes 1010 may be attached to the suction (return) line of the refrigerant to measure the temperature of the returning refrigerants, for example. In some cases, probe 1010 may also measure the pressure of the refrigerants inside the pipe. Similarly, probe 1011 may measure the temperature of the liquid (supply) line of the refrigerant, for example. In some cases, probe 1011 may also measure the pressure of the refrigerants inside the piping. Probe 1012 may measure the temperature of the condenser fins and/or the compressor fins, for example. As another example, probe 1014 may measure ambient temperature, humidity, and atmospheric pressure. The current transformer 1013 may measure the amount of current being drawn by the compressor/condenser, thus measuring the actual energy consumed by the equipment. The data form all these sensors 1010-1014 may be continuously streamed to a remote server 1015 via the internet, as disclosed hereinbefore. At the server, the data may be fed into algorithms which determine whether or not the HVAC is functioning optimally as well as whether or not the measured energy savings, are close the expected energy savings. In an example, the algorithm may be simple. For example, if the HVAC manufacturer states that the optimal run time for each compressor ON cycle is 15 minutes, but the streamed data shows the average compressor ON run time is 25 mins for example, then the user knows that the compressor is undersized or that the compressor is not running optimally and is wasting energy, or needs a tune up, etc.

All the MVDRs as well as the actual savings they record may be shown on the web interface 1016, which utility companies or its aggregators may have access to. The information available on the web interface 1016 may be very useful for the utility providers, as it may enable them to assess if an energy saving measure is worth the rebates the providers offer. It should be understood that the MVDRs displayed on the web interface may be integrated with various appliances or energy consuming equipment, which are not limited to HVAC systems, as disclosed in greater detail when referring to FIGS. 11a -c.

FIGS. 11a-c illustrate additional exemplary MVDR installs, wherein the MVDR is integrated into a refrigeration unit, lighting appliance, and pool pump, according to an aspect. As shown by FIG. 11a , an MVDR, such as MVDR4 1101, may be installed in industrial and commercial refrigeration units, which may be used to cool and store disposable produce, meats, drinks, and other food items, for example. Commercial refrigerator units 1100 may be similar to HVAC compressor/condenser units. Thus, MVDR4 1101 has probes and sensors which measure the temperature and/or pressure of the refrigerant lines. For example, a current transformer 1102 may be present to measure the amount of electricity the refrigerator is using. Additionally, probe 1103 may be attached to the refrigerant line between the compressor 1108 and condenser 1104, such that the probe 1103 is as close to the compressor as possible, and may measure the temperature and/or pressure of the refrigerants medium. Probe 1106 may be attached to the capillary tube between the condenser 1104 and the evaporator 1105 and measure the temperature of the medium inside the capillary tube, for example. Probe 1107 may measure the temperature and or pressure of the refrigerant medium inside the return line to the compressor 1108. MVDR4 1101 may stream the data from the probes 1102, 1103, 1106, 1107 to a remote server 1015 of FIG. 10b , where the energy usage and performance of the industrial refrigerators can be measured and verified accurately in real time.

As shown in FIG. 11b , another exemplary application may be an MVDR5 1110 installed in a facility to monitor, measure, and verify the energy consumed or saved by Third Party Devices integrated with lightings and appliances 1114-1116. Various current transformers 1111-1113 may be installed in the power lines of the energy consuming equipment 1114-1116, such that the current transformers 1111-1113 measure the amount of energy the equipment is actually consuming, as disclosed hereinbefore. The MVDR5 1110 may also control a set of contactors and relays switches 1117, which may also be controlled by Third Party Devices, for example. Again, it should be understood that real time energy savings data may be streamed to remote server 1015 of FIG. 10b to measure and verify the actual energy consumed or saved.

As shown in FIG. 11c , another exemplary application may be an MVDR6 1124 integrated with a pool pump 1120. Similar to the other MVDR applications, MVDR6 1124 may have a temperature sensor 1121, current transformer 1122, and may control contactors or relays 1123. Sensor 1121 may measure the actual temperature of the water in the pool. Current transformer 1122 may measure the actual electricity used by the pool pump. MVDR6 1124 may turn the pool pumps on or off using the contactors 1123, depending on the settings set by a user in step 914 in FIG. 9 or depending on a set of demand response settings, for example. Again, it should be understood that measurements and verification of actual energy consumed or saved may be streamed to a remote server 1015 of FIG. 10 b.

Thus, it should be understood that an MVDR has many applications and may be integrated with any energy consuming equipment. It should also be understood that, when an MVDR is integrated with energy consuming equipment, the MVDR may be configured to be a wireless (e.g., Wi-Fi) enabled circuit device for open automated demand response capability (“DR/ADR”). Thus, the cumbersome, challenging and/or expensive task of replacing the entire thermostat is eliminated and the goal of implementing a DR/ADR approach to save energy is achieved. It should be noted that, while the description herein primarily discloses the use of Wi-Fi, it should be apparent that other wireless communication protocols (e.g., Bluetooth™ RF, Zigbee™, etc.) may be used instead of Wi-Fi.

In addition to providing equipment with a wireless (e.g., Wi-Fi) enabled circuit device for open automated demand response capability, the MVDR may be configured to provide circuitry for ensuring energy efficient operation of the HVAC system outside of a demand response occurrence, thus further saving energy, as disclosed hereinbefore. For example, an MVDR with wireless (e.g., Wi-Fi) enabled automatic demand response (ADR) may extend the fan run time after a heating or cooling unit has shut off in addition to providing a compressor rest when the compressor has been running continuously for a period of time. More specifically, as an example, the controller may be a Wi-Fi enabled efficient fan controller device with firmware algorithms which read commands from a secured URL site, write the status of the MVDR and thermostat outputs to another secured URL website, and have the MVDR execute on the commands in accordance to the read commands.

Another advantage may be that the MVDR device can be connected between an existing thermostat and the air handler of an HVAC system, such that the automated demand response can be implemented without the need to replace the thermostat. Additionally, as disclosed herein, the MVDR device may also provide blower fan extended runtime to save energy during regular operations, which may be outside of a demand response occurrence. The blower fan runtime may automatically be extended based on how long the air conditioning compressor has been running and how long the compressor has been off, for example. In the case of heating, the blower fan runtime may also be automatically extended based on gas valve activation time, furnace operating time, or Heat Pump activation time and how long the heating elements were off, for example.

As another example, the duration of time the fan continues to operate after the heating element is off or after the air conditioner compressor is off may vary with the duration of time the heating element or compressor were on an off, as measure over many cycles by microprocessors and firm wares, as disclosed herein. The additional fan run time associated with the heating element may relate to the quantity of left over heat stored in the heat exchanger. The additional run time associated with the air conditioner compressor may relate to the quantity of cold water condensed on the evaporator coil, for example. Hence, the MVDR may recover and deliver more heating and cooling energy to a conditioned space than would be possible with original HVAC fan controllers. The MVDR may improve the efficiency of HVAC equipment by delivering additional heating or cooling capacity for a small amount of additional electric energy (kWh).

Again, it should be understood that for the MVDR to work universally, it may need to interface with every one of a manufacturers thermostats used within an HVAC system. In many of a manufacturers' thermostats, the fan output command signal may go into a floating or unknown state when the thermostat is shut off by putting the thermostat switch to system off. In such a case, if an MVDR is connected to the thermostat, the fan command signal being in an unknown state could be read as an ON state, and the MVDR can turn the fan on and run continuously. Therefore, as described herein, the MVDR circuitry may be configured to read any unknown or floating signals from the thermostat fan command signal as known 24 vac or 0 vac state. In this way, the fan may always be turned off when the signal is not at an ON state.

It may be advantageous to set forth definitions of certain words and phrases used in this patent document. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and/or. The phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like.

As used in this application, “plurality” means two or more. A “set” of items may include one or more of such items. Whether in the written description or the claims, the terms “comprising,” “including,” “carrying,” “having,” “containing,” “involving,” and the like are to be understood to be open-ended, i.e., to mean including but not limited to.

Throughout this description, the embodiments and examples shown should be considered as exemplars, rather than limitations on the apparatus and procedures disclosed or claimed. Although many of the examples involve specific combinations of method acts or system elements, it should be understood that those acts and those elements may be combined in other ways to accomplish the same objectives. With regard to flowcharts, additional and fewer steps may be taken, and the steps as shown may be combined or further refined to achieve the described methods. Acts, elements and features discussed only in connection with one embodiment are not intended to be excluded from a similar role in other embodiments.

For means-plus-function limitations recited in the claims, the means are not intended to be limited to the means disclosed in this application for performing the recited function, but are intended to cover in scope any means, known now or later developed, for performing the recited function.

Further, in describing representative embodiments of the present invention, the specification may have presented the method and/or process of the present invention as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. As one of ordinary skill in the art would appreciate, other sequences of steps may be possible. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. In addition, the claims directed to the method and/or process of the present invention should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the present invention.

Although specific embodiments have been illustrated and described herein for the purpose of disclosing the preferred embodiments, someone of ordinary skills in the art will easily detect alternate embodiments and/or equivalent variations, which may be capable of achieving the same results, and which may be substituted for the specific embodiments illustrated and described herein without departing from the scope of the invention. Therefore, the scope of this application is intended to cover alternate embodiments and/or equivalent variations of the specific embodiments illustrated and/or described herein. Hence, the scope of the invention is defined by the accompanying claims and their equivalents. Furthermore, each and every claim is incorporated as further disclosure into the specification and the claims are embodiment(s) of the invention. 

What is claimed is:
 1. An energy saving controller for overriding a thermostat, the energy saving controller being configured for mounting between the thermostat and a controller for an air handler unit having a fan and an HVAC component selected from the group consisting of a heater and a compressor, the energy saving controller comprising a wireless module for wirelessly connecting to a wireless router connected to Internet, the energy saving controller being configured to control the air handler unit based on a demand response request sought and retrieved by the energy saving controller from a utility provider via the Internet, the energy saving controller being further configured to stream in real-time to a remote server data about actual amount of energy consumed by the air handler unit, thus allowing a user of the air handler unit and also the utility provider to see the actual amount of energy consumed by the air handler unit, and thus verify that the air handler unit saves an expected amount of energy.
 2. The energy saving controller of claim 1, wherein the control of the air handler unit is further based on an input from a probe.
 3. The energy saving controller of claim 2, wherein the probe is a temperature probe.
 4. The energy saving controller of claim 1, further being configured to periodically report via the Internet to the utility provider the ON and OFF status of the air handler unit.
 5. The energy saving controller of claim 4, wherein the energy saving controller is configured to seek and retrieve the demand response request by periodically accessing and reading commands from a READ URL of the utility provider and wherein the reporting occurs by periodically accessing and writing to a WRITE URL, thus without access by the utility provider to the energy saving controller.
 6. The energy saving controller of claim 1, further being configured to extend the fan run time after the HVAC component has shut off, when outside of a demand response occurrence.
 7. The energy saving controller of claim 1, further being configured to provide also compressor rest if the compressor has been running continuously for a period of time.
 8. The energy saving controller of claim 1, further being configured to monitor ON and OFF durations of the HVAC component, in a first cycle, and, of ON duration of a second cycle immediately following the first cycle, and determining the fan's first run time extension based on the ON and OFF durations of the first cycle and the ON duration of the second cycle.
 9. The energy saving controller of claim 1, further being configured for shutting down the HVAC component for a first predetermined duration and means for overriding determining of the fan's first run time extension amount if the HVAC component have run continuously for a second predetermined duration during the current cycle, while allowing the fan to run for a fan's second run time extension amount equal with the first predetermined duration.
 10. The energy saving controller of claim 1, further comprising circuitry configured to process a floating state thermostat fan output signal, received by the energy saving controller from the thermostat, into an OFF state signal, to avoid the floating state thermostat fan output signal to falsely trigger the fan to turn ON.
 11. An energy saving controller being configured for electrical connection to energy consuming equipment, the energy saving controller comprising a wireless module configured to wirelessly connect to a wireless router connected to Internet, the energy saving controller being further configured to control the energy consuming equipment based on a demand response request issued by a utility provider and accessed via the Internet by the energy saving controller, such that the control of the energy consuming equipment based on the demand response request occurs without access by the utility provider to the energy saving controller or to the energy consuming equipment.
 12. The energy saving controller of claim 11, wherein the control of the energy consuming equipment is further based on an input from a probe.
 13. The energy saving controller of claim 12, wherein the probe is a temperature probe.
 14. The energy saving controller of claim 11, wherein the energy consuming equipment is refrigeration equipment.
 15. The energy saving controller of claim 11, further being configured to receive an input from a current sensor associated with a power line feeding the energy consuming equipment and to stream in real-time to a remote server data about actual amount of energy consumed by the energy consuming equipment.
 16. The energy saving controller of claim 15, wherein the current sensor is a current transformer that measures the amount of energy consumed by the energy consuming equipment.
 17. The energy saving controller of claim 11, further being configured to stream in real-time to a remote server data about actual amount of energy consumed by the energy consuming equipment, thus allowing a user and a utility provider to see the actual amount of energy consumed by the energy consuming equipment, and thus verify that the energy consuming equipment saves an expected amount of energy.
 18. An energy saving controller being configured for electrical connection to energy consuming equipment, the energy saving controller comprising a wireless module configured to wirelessly connect to a wireless router connected to Internet, the energy saving controller being further configured to allow a user to control the energy consuming equipment via the Internet, the energy saving controller being further configured to receive an input from a current sensor associated with a power line feeding the energy consuming equipment and to stream in real-time to a remote server data about actual amount of energy consumed by the energy consuming equipment, thus allowing the user and a utility provider to see in real-time the actual amount of energy consumed by the energy consuming equipment, and thus verify that the energy consuming equipment saves an expected amount of energy. 